.TH killsnoop.bt 8  "2018-09-07" "USER COMMANDS"
.SH NAME
killsnoop.bt \- Trace signals issued by the kill(),tkill(),tgkill() syscall.
Uses bpftrace/eBPF.
.SH SYNOPSIS
.B killsnoop.bt
.SH DESCRIPTION
killsnoop traces the kill(),tkill(),tgkill() syscall, to show signals sent via
this method. This may be useful to troubleshoot failing applications, where an
unknown mechanism is sending signals.

This works by tracing the kill(),tkill(),tgkill() syscall tracepoints.

Since this uses BPF, only the root user can use this tool.
.SH REQUIREMENTS
CONFIG_BPF and bpftrace.
.SH EXAMPLES
.TP
Trace all kill(),tkill(),tgkill() syscalls:
#
.B killsnoop.bt
.SH FIELDS
.TP
TIME
Time of the kill call.
.TP
PID
Source process ID
.TP
COMM
Source process name
.TP
SIG
Signal number or name. See signal(7).
.TP
TPID
Target process ID
.TP
RESULT
Result. 0 == success, a negative value (of the error code) for failure.
.SH OVERHEAD
This traces the kernel kill function and prints output for each event. As the
rate of this is generally expected to be low (< 100/s), the overhead is also
expected to be negligible. If you have an application that is calling a very
high rate of kill()|tkill()|tgkill()s for some reason, then test and understand
overhead before use.
.SH SOURCE
This is from bpftrace.
.IP
https://github.com/bpftrace/bpftrace
.PP
Also look in the bpftrace distribution for a companion _examples.txt file containing
example usage, output, and commentary for this tool.

This is a bpftrace version of the bcc tool of the same name. The bcc tool
may provide more options and customizations.
.IP
https://github.com/iovisor/bcc
.SH OS
Linux
.SH STABILITY
Unstable - in development.
.SH AUTHOR
Brendan Gregg, Rong Tao
.SH SEE ALSO
opensnoop.bt(8)
